Force explicit signing in Makefile version bump targets#66
Merged
Conversation
Member
Author
Review SummaryVerdict: APPROVE Findings
|
Merged
sebastientaggart
added a commit
that referenced
this pull request
Apr 8, 2026
…signing Force explicit signing in Makefile version bump targets
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version-bump targets previously relied on ambient
commit.gpgsign/tag.gpgsignconfig. In sandboxed shells that signing can silently skip, producing an unsigned bump commit (while the tag still signs) — which breaks GitHub's Verified badge on the Release, as happened with v0.3.7.Switches
bump-patch,bump-minor,bump-major, andset-versiontogit commit -Sandgit tag -sso signing is explicit. If no key is available, the recipe fails loudly instead of producing an unsigned commit.Issue #65